home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941221-19950208
/
000072_news@columbia.edu_Mon Jan 2 17:43:03 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA05115
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 2 Jan 1995 12:43:04 -0500
Received: by apakabar.cc.columbia.edu id AA19352
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 2 Jan 1995 12:43:03 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit & the strange DOS machine
Date: 2 Jan 1995 17:43:03 GMT
Organization: Columbia University
Lines: 49
Message-Id: <3e9dv7$isl@apakabar.cc.columbia.edu>
References: <wpfulmorD1pIp4.Aon@netcom.com>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <wpfulmorD1pIp4.Aon@netcom.com>,
william p fulmor <wpfulmor@netcom.com> wrote:
>I have a single board 8 mhz 8088 MSDOS computer which is an expansion
>board to a unix based computer. COM1 is irrevocably tied to a
>non-standard on-board-modem. COM2 is said to be a standard PC serial
>port, which *was* driven by an NS 8250. COM2 is *now* driven by an NS
>16550. \|^)
>
>After starting Kermit (3.13 patch 20) in the usual fashion, ...
>
Please try 3.14 Beta. There have been many improvements in the RS-232
(dealing with modem signals) area, which might affect your situation.
Anonymous ftp to kermit.columbia.edu, directory kermit/test/bin, binary
mode, file mstibm.zip. Unzip with "-d" switch. Read top-level READ.ME
to get started.
>...
>1. Kermit takes 13 minutes from pressing <return> following the dial
>command to actually dialing the number.
>
This sounds like repeated flow-control failures and long timeout waits
(about 15 seconds each). This probably means that Kermit has been told
to SET FLOW RTS/CTS prior to dialing, but that the modem has not been
configured for RTS/CTS, or does not use it properly while in command mode.
Try SET FLOW NONE during dialing, and then (if it works) change to SET
FLOW RTS/CTS after dialing is complete.
>2. Escaping from connect to local is prompt, but connecting back to
>remote takes a *long* time.
>
Again, it sounds like your modem is not asserting CTS at the time when
CONNECT. Make sure Kermit and the modem are *both* set for RTS/CTS
flow control. If that doesn't help, I'd say the modem is probably not
working right -- or your cable does not connect the RTS and CTS terminals
on each side to their counterparts on the other.
>3. In interactive operation as a vt100 and with 'set flo rts/cts' a
>very few characters are dropped, not enough to cause problems - but - The
>screen is written only a few lines at a time with long pauses in
>between.
>
Same deal, again.
- Frank
x
x